• WardrobeManager.Api/Migrations/20260227172446_AddSizeToClothingItem.Designer.cs: Language not supported

WardrobeManager.Api/Endpoints/ClothingEndpoints.cs:41

• This endpoint uses Debug.Assert(user != null) and then dereferences user.Id. In Release builds the assert is removed, so a missing user in HttpContext.Items will become a null dereference and 500. Return an explicit 401/403 (or problem response) when the middleware did not populate the user.

        User? user = context.Items["user"] as User;
        Debug.Assert(user != null, "Cannot get user");

        var clothes = await clothingService.GetAllClothingAsync(user.Id);

WardrobeManager.Api/Endpoints/ClothingEndpoints.cs:48

• IMapper mapper is injected into this handler but never used. Remove the unused parameter to avoid unnecessary DI resolution and to keep the handler signature focused.

    public static async Task<IResult> AddNewClothingItem(
        [FromBody] NewClothingItemDTO newClothingItem,
        HttpContext context, IClothingService clothingService, IMapper mapper
    )

WardrobeManager.Presentation/ViewModels/AddClothingItemViewModel.cs:55

• UploadImage allocates a MemoryStream but never disposes it. Since this can hold multi‑MB buffers, use using/await using to dispose the stream after converting to base64.
  WardrobeManager.Api/Services/Implementation/FileService.cs:44
• The file size exception message divides by 1024 but labels the result as MB, which will report KB values as MB. Convert bytes to MB using 1024 * 1024 (or adjust the label) so operators/users get accurate diagnostics.

        if (imageBytes.Length > maxFileSizeNum)
        {
            throw new Exception(
                $"File size too large! Received file size: {imageBytes.Length / 1024} MB. Max file size: {maxFileSizeNum / 1024} MB");
        }

WardrobeManager.Api/Endpoints/ClothingEndpoints.cs:66

• IMapper mapper is also injected here but unused. Remove it from this handler signature as well.

    public static async Task<IResult> DeleteClothingItem(
        [FromBody] int itemId,
        HttpContext context, IClothingService clothingService, IMapper mapper
    )

WardrobeManager.Api/Services/Implementation/FileService.cs:73

• DeleteImage is declared async but has no awaits (all operations are synchronous). Consider removing async and returning Task.CompletedTask (or making the file move async) so the signature accurately reflects behavior.

    public async Task DeleteImage(Guid givenGuid)
    {
        var guid = ParseGuid(givenGuid);
        string path = Path.Combine(dataDirectoryService.GetUploadsDirectory(), guid);
        string deletePath = Path.Combine(dataDirectoryService.GetDeletedUploadsDirectory(), guid);

WardrobeManager.Presentation/ViewModels/AddClothingItemViewModel.cs:5

• Avoid referencing CommunityToolkit.Mvvm.ComponentModel.__Internals; it's not a public API surface and can break on package updates. Remove this using (and any dependent usage) and rely on the public CommunityToolkit.Mvvm.ComponentModel APIs instead.
  WardrobeManager.Presentation/ViewModels/AddClothingItemViewModel.cs:65
• The config value WM_MAX_IMAGE_UPLOAD_SIZE_IN_MB is parsed with Convert.ToInt32 but only IOException is caught. If the value is missing/invalid (e.g., non-numeric), this will throw and bypass the notification path. Handle parsing failures (e.g., int.TryParse) and/or broaden the catch to show a user-friendly error.
  WardrobeManager.Presentation/Layout/NavMenu.razor:57
• Wrapping a <Button> inside an <a href> creates nested interactive elements (invalid HTML) and can cause accessibility and click/keyboard issues. Prefer NavLink or have the button trigger navigation directly instead of <a><Button/></a>.

                                <a href="/wardrobe">
                                        <Button Type="ButtonType.Outline"
                                                Text="My Wardrobe"
                                                Icon="Person"/>
                                </a>

WardrobeManager.Api/Services/Implementation/FileService.cs:5

• SQLitePCL is imported here but not used. Remove the unused using to avoid IDE/analysis noise and keep dependencies clear.

#region

using SQLitePCL;
using WardrobeManager.Api.Services.Interfaces;

WardrobeManager.Api/Middleware/UserCreationMiddleware.cs:30

• NameIdentifier is defaulted to an empty string and then passed into GetUser, which can cause unnecessary lookups and can hide missing-claim issues. Skip the lookup when the claim is null/empty so context.Items["user"] is only set when you have a valid user id.

        var userService = context.RequestServices.GetRequiredService<IUserService>();
        var userId = context.User.FindFirst(ClaimTypes.NameIdentifier)?.Value ?? "";

        var user = await userService.GetUser(userId);
        if (user != null)

WardrobeManager.Shared/StaticResources/StaticValidators.cs:20

• StaticValidators.Validate adds new shared validation behavior used across layers, but there are no unit tests covering null input, missing validators, or aggregated error messages. Add tests in WardrobeManager.Shared.Tests to lock down this behavior and avoid regressions.
  WardrobeManager.Presentation/Services/Implementation/ApiService.cs:30
• There are existing unit tests for ApiService, but the newly added clothing methods are not covered. Add tests for the new GET/POST clothing calls (including error responses) to keep coverage consistent for this service.